<?php
/**
 * <https://y.st./>
 * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. Sf not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'title' => "...
	are some $a[gTLD]s actually within my reach?",
	'body' => <<<END
<p>
	Going back through the six domain registries that I thought did not ask for a telephone number, I found that not only did one of them ask for a telephone number, it <strong>*required*</strong> one.
	The issue was that I didn&apos;t notice that before registering the domain, you must register the domain contacts separately.
	Sadly, I&apos;ve had to downgrade the <a href="/en/URI_research/ccTLDs.xhtml#hm"><code>//hm.</code> registry</a> from being one of my most recommended six to being completely unusable.
	The other five do not appear to have this same issue, thankfully.
</p>
<p>
	I found at least three potentially-usable registries today, though due to a bit of excitement, I may have found others and forgotten them.
	None of the usable $a[ccTLD]s were particularly noteworthy though.
	The <a href="/en/URI_research/usable_ccTLDs.xhtml#tg">Togolese Republic</a>, <a href="/en/URI_research/usable_ccTLDs.xhtml#vi">Virgin Islands of the United States</a>, and <a href="/en/URI_research/usable_ccTLDs.xhtml#co.ve">Bolivarian Republic of Venezuela</a> all ask for a telephone number and refuse to allow you to leave that field blank, but they allow you to enter strings saying that you do not have telephone service.
</p>
<p>
	The really interesting thing I found today was a registrar that also allows one to specify that he/she does not have a telephone number by setting the telephone number field to a non-telephone-number string.
	This registrar sells <code>//com.</code>, <code>//info.</code>, <code>//net.</code>, and <code>//org.</code> domains.
	This registrar&apos;s prices are comparatively high, and I don&apos;t know if they include $a[DNS] servers, but if I absolutely need to get a domain under a $a[gTLD], they could help me out.
	Unless I were to attempt to place an order, I can&apos;t be sure that the actual registries would accept the registration with a non-numeric telephone number value, but I really want to think that I&apos;ve found a place that allows such registration.
	More importantly, should I tell people about this discovery? If I don&apos;t tell anyone, than this discovery is of no value.
	I would be happier using a domain that allowed me to outright leave the telephone number field blank, or even better, did not ask me for a telephone number at all.
	On the other hand, if I tell people, than this potential loophole could get closed.
	Not only would $a[IANA] be upset that there is a way to register a name under a $a[gTLD] and want to fix it, but there are also those that would directly oppose me and my goals.
	Some people feel I&apos;m childish for trying to escape the telephone number system and might want to through whatever obstetrical they can into my path.
	Other people are outright trolls and would see this as an opportunity to mess with me not because they even know who I am, but just because they <strong>*can*</strong> mess with me.
	I will keep the exact details of my discovery to myself for now while I think on this, only writing here that the discovery was made at all.
</p>
<p>
	I&apos;ve finished compiling my $a[ccTLD] research, and will start the next phase tomorrow.
	I&apos;ve sorted out the usable $a[ccTLD]s from the unusable, but continuing on, I only want to focus on the cream of the crop, the five most forward-thinking $a[ccTLD] registries available.
	There&apos;s no point in further research on the unusable ones, and research is exhausting, so I&apos;d rather not pour a whole lot of energy into the lesser-but-still-usable registries either, especially right after having looked into every $a[ccTLD] in existence.
</p>
<p>
	My Oregon tax return check arrived today, though not the tax return check from the $a[IRS].
	I had actually forgotten all about the tax return checks because I&apos;ve been busy, but maybe also because this is the wrong time of year to receive them.
</p>
<p>
	Malaria researchers may have discovered <a href="http://www.medicaldaily.com/malaria-parasite-cancer-cure-weve-been-looking-accidental-discovery-displays-357302">the beginnings of a new treatment for cancer</a>.
	I won&apos;t jump to conclusions and call it a cure just yet, but it&apos;s something to look forward to.
	My biggest fear though is that it will be pattented and horded instead of actually being used to help people.
</p>
<p>
	It seems that because <a href="http://wowana.me/">wowaname</a>&apos;s website is not accessible over $a[HTTPS] and mine is, attempting to connect to her website over $a[HTTPS] results in reaching my website on her domain.
	I hadn&apos;t really thought about the effects of her setting up $a[HTTPS] on her server for me, but I suppose that result makes sense.
	It would either be that or reaching her website on her domain using my certificate, assuming she didn&apos;t explicitly set up $a[HTTPS] service on her website to correct the anomaly.
</p>
<p>
	My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
</p>
END
);
